fix(nextjs): Add turbopackIgnore to @clerk/ui dynamic import for Turbopack compatibility#7805
Conversation
…urbopack compatibility
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 6493721 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📝 WalkthroughWalkthroughThe Next.js 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
…opack compatibility (#7805)
…opack compatibility (#7805)
Summary
/* turbopackIgnore: true */magic comment alongside existing/* webpackIgnore: true */on the dynamicimport('@clerk/ui/entry')in the Next.js ClerkProviderwebpackIgnorecomment prevents webpack from statically resolving the optional@clerk/uidependency at build time, but Turbopack does not recognize it — causing the bare specifier to reach the browser and fail withTypeError: Failed to resolve module specifier '@clerk/ui/entry'turbopackIgnorein next.js#69768 (available since Next.js 15 RC.2), so using both comments ensures the import is skipped by both bundlers when@clerk/uiis not installedTest plan
uiprop works in a Next.js app with Turbopack (Next.js 16 default)@clerk/uiinstalled (no regression from webpack)